[1.4.0] - 2023-07-21
(https://s3drive.app/changelog), it can be enabled in the Settings (it's called E2E on our end, but it's essentialy 1:1 compatible).
Most recent release: [1.7.0] - 2023-12-29
provides full integration with Rclone allowing you to use 70+ back-ends on top of S3 (more on that here: https://docs.s3drive.app/setup/import_rclone/). One of the back-ends is crypt
(https://rclone.org/crypt/) which means you can use S3Drive to encrypt your data and store it on Dropbox or whenever you want.
In a 1.7.1
release which we will release in a few days there will be an option to sync from local file system as well as (on Android, iOS and macOS this option won't be initially available due to different permission systems, we'll need to provide workaround), between different back-ends, so you can e.g. upload some files to Dropbox, some files to Google Cloud and then sync certain folders between them as you need. (edited)1.7.1
release is now a thing !
We love the idea of permissions to only specific folder, the challenge is that these operate on so called Content URIs instead of classic file system (you can notice on your video it starts with content://).
That makes it incompatible with classic software, Rclone included.
That's why our best solution so far is to aim for MANAGE_EXTERNAL_STORAGE
permission which fortunately and unfortunately gives access to the filesystem: https://developer.android.com/training/data-storage/manage-all-files#operations-allowed-manage-external-storage
In the long run we could reimplement some syncing logic and make it compatible with these Content URIs... but since Rclone does damn good job already we're not really keen to reinvent the wheel, add maintenance/risks and spend at least couple months initially just to get it right. (edited)rclone
route? I was looking around and found this other good idea around Cryptomator integration https://github.com/rclone/rclone/issues/71924. No path protection
as flagged in the: https://github.com/rclone/rclone/issues/7192
With my current knowledge I think that Rclone approach is better, since its simpler (complexity is an enemy in security field), robust and less prone to corruption/data loss.